User interface for providing assistance related to health

ABSTRACT

In one aspect, a method related to health-related data management. In addition to the foregoing, other method and system and program product aspects are described in the claims, drawings, and text forming a part of the present application.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to, claims the earliest availableeffective filing date(s) from (e.g., claims earliest available prioritydates for other than provisional patent applications; claims benefitsunder 35 USC § 119(e) for provisional patent applications), andincorporates by reference in its entirety all subject matter of thefollowing listed application(s) (the “Related Applications”) to theextent such subject matter is not inconsistent herewith; the presentapplication also claims the earliest available effective filing date(s)from, and also incorporates by reference in its entirety all subjectmatter of any and all parent, grandparent, great-grandparent, etc.applications of the Related Application(s) to the extent such subjectmatter is not inconsistent herewith. The United States Patent Office(USPTO) has published a notice to the effect that the USPTO's computerprograms require that patent applicants reference both a serial numberand indicate whether an application is a continuation or continuation inpart. Stephen G. Kunih, Benefit of Prior-Filed Application, USPTOElectronic Official Gazette, Mar. 18, 2003 athttp:H/www.uspto.gov/web/offices/com/sol/og/2003/week 11/patbene.htm.The present applicant entity has provided below a specific reference tothe application(s)from which priority is being claimed as recited bystatute. Applicant entity understands that the statute is unambiguous inits specific reference language and does not require either a serialnumber or any characterization such as “continuation” or“continuation-in-part.” Notwithstanding the foregoing, applicant entityunderstands that the USPTO's computer programs have certain data entryrequirements, and hence applicant entity is designating the presentapplication as a continuation in part of its parent applications, butexpressly points out that such designations are not to be construed inany way as any type of commentary and/or admission as to whether or notthe present application contains any new matter in addition to thematter of its parent application(s).

RELATED APPLICATIONS

-   1. For purposes of the USPTO extra-statutory requirements, the    present application constitutes a continuation in part of currently    co-pending United States patent application entitled Providing    Assistance Related to Health, naming Edward K. Y. Jung, Royce A.    Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., and    Lowell L. Wood, Jr., as inventors, USAN: To be Assigned, filed Nov.    17, 2005.-   2. For purposes of the USPTO extra-statutory requirements, the    present application constitutes a continuation in part of currently    co-pending United States patent application entitled User Interface    for Providing Assistance Related to Health, naming Edward K. Y.    Jung, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.    Rinaldo, Jr., and Lowell L. Wood, Jr., as inventors, USAN: To be    Assigned, filed Nov. 22, 2005, contemporaneously herewith.

TECHNICAL FIELD

The present application relates, in general, to health-related datamanagement.

SUMMARY

In one aspect, a method related to health-related data managementincludes but is not limited to providing an interface to enable a vendorand/or a publisher to change one or more health regimen data entities;and accepting input to the interface. In addition to the foregoing,other method aspects are described in the claims, drawings, and textforming a part of the present application.

In one aspect, a system related to health-related data managementincludes but is not limited to circuitry for providing an interface toenable a vendor and/or a publisher to change one or more health regimendata entities; and circuitry for accepting input to the interface. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the present application.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming and/or electromechanical devicesand/or optical devices for effecting the herein-referenced methodaspects; the circuitry and/or programming and/or electromechanicaldevices and/or optical devices can be virtually any combination ofhardware, software, and/or firmware configured to effect the hereinreferenced method aspects depending upon the design choices of thesystem designer skilled in the art.

In one aspect, a program product includes but is not limited to a signalbearing medium bearing one or more instructions for providing aninterface to enable a vendor and/or a publisher to change one or morehealth regimen data entities; and one or more instructions for acceptinginput to the interface. In addition to the foregoing, other programproduct aspects are described in the claims, drawings, and text forminga part of the present application.

In addition to the foregoing, various other method, system, and/orprogram product aspects are set forth and described in the teachingssuch as the text (e.g., claims and/or detailed description) and/ordrawings of the present application.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent in theteachings set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts one implementation of an exemplary environment in whichthe methods and systems described herein may be represented;

FIG. 2 depicts alternative exemplary embodiments;

FIG. 3 illustrates alternative exemplary embodiments;

FIG. 4 illustrates alternative exemplary embodiments;

FIG. 5 depicts alternative exemplary aspects of embodiments;

FIG. 6 depicts an exemplary view of aspects of an embodiment;

FIG. 7 depicts an alternative exemplary view of the aspects of theembodiment depicted in FIG. 6;

FIG. 8 depicts an exemplary view of aspects of an embodiment;

FIG. 9 depicts an alternative exemplary view of the aspects of theembodiment depicted in FIG. 8;

FIG. 10 depicts an exemplary view of aspects of an embodiment.

FIG. 11 depicts an alternative exemplary view of aspects of theembodiment depicted in FIG. 10;

FIG. 12 depicts a high-level logic flowchart of an operational process;

FIG. 13 shows several alternative implementations of the high-levellogic flowchart of FIG. 12;

FIG. 14 shows several alternative implementations of the high-levellogic flowchart of FIG. 13; and

FIG. 15 shows several alternative implementations of the high-levellogic flowchart of FIG. 12.

The use of the same symbols in different drawings typically indicatessimilar or identical items.

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary environment 100 in which embodiments maybe used. The end-user 102 is a person who wishes to access informationregarding pharmaceutical, nutraceutical, veterinary, dietary, and/ornutritional substances, procedures, processes, and/or practices ofinterest. The end-user interface device 104 may be a keyboard, mouse,trackball, monitor, microphone and speakers, and/or other interfacedevice or devices for a human to interface with the end-user logic 106of computer 108. The end-user logic 106 may include at least a portionof the hardware/software/firmware of the computer 108. The computer 108may be used by the end-user 102 to access such information via anothercomputer or computers represented by the network 110.

Vendor 112 is a person and/or persons and/or entity and/or entities thatmay supply pharmaceutical, nutraceutical, veterinary, dietary, and/ornutritional substances, procedures, processes, and/or practices ofinterest. The vendor interface device 114 may be a keyboard, mouse,trackball, monitor, microphone and speakers, and/or other interfacedevice or devices for a human to interface with the vendor logic 116 ofcomputer 118. The vendor logic 116 may include at least a portion of thehardware/software/firmware of the computer 118. The vendor 112 may usethe computer 118 to provide information and channels, making the vendor112 available to provide pharmaceutical, nutraceutical, veterinary,dietary, and/or nutritional substance, procedure, processes, and/orpractices of interest, via another computer or computers represented bythe network 110, to, among others, the end-user 102.

Publisher 120 is a person and/or persons and/or entity and/or entitiesthat may supply information about pharmaceutical, nutraceutical,veterinary, dietary, and/or nutritional substances procedures,processes, and/or practices of interest, and/or about authorities havingexpertise or claimed expertise regarding pharmaceutical, nutraceutical,veterinary, dietary, and/or nutritional substances procedures,processes, and/or practices of interest. The publisher interface device122 may be a keyboard, mouse, trackball, monitor, microphone andspeakers, and/or other interface device or devices for a human tointerface with the publisher logic 124 of computer 126. The publisherlogic 124 may include at least a portion of thehardware/software/firmware of the computer 126. The publisher 120 mayuse the computer 126 to provide such information about pharmaceutical,nutraceutical, veterinary, dietary, and/or nutritional substance,procedure, processes, and/or practices of interest, via another computeror computers represented by the network 110, to, among others, theend-user 102. The publisher 120 represents a wide variety of informationproviders, including but not limited to magazine publishers, bookpublishers, website maintainers, weblog proprietors, experts, researchorganizations, and users of the pharmaceutical, nutraceutical,veterinary, dietary, and/or nutritional substances procedures,processes, and/or practices of interest.

End-users 102, vendors 112, and publishers 120 are not mutuallyexclusive categories. One person, group of persons, entity, or group ofentities may be categorized as an end-user 102, vendor 1 12, and/orpublisher 120 simultaneously or at different times. End-users 102,vendors 112, and publishers 120 are exemplary parties and do notrepresent all users. Exemplary descriptions including the end-user 102are not limiting and do not preclude use of an embodiment by vendors 112and/or publishers 120.

FIG. 2 depicts alternative exemplary embodiments of a data entity,including depiction of alternative exemplary embodiments of healthregimen data entities associated with some amount of additionalinformation. This additional information may include but is not limitedto an item of associative information, e.g., a linkage or a resolvablereference, to one or more other health regimen data entities in the datastructure/data structures (e.g., which may be distributed datastructures), e.g., a pointer, identifier, and/or a link. In FIG. 2 andthe other figures, items of associative data are depicted by linesand/or arrows between health regimen data entities, or are implicit ofthe relationship between a nesting health regimen data entity and anyhealth regimen data entity nested within or at any depth; such implicititems of associative data are shown by the illustrated nesting. Theadditional information may also include but is not limited tosubstantive information, e.g., where the health regimen data entityincludes the identity of a substance and the additional informationdescribes a potential use or specifies a dosage. Here health regimendata entity 202 includes an identifier for the element lithium (Li). Thehealth regimen data entity 204 illustrates an alternative exemplaryembodiment of the health regimen data entity 202. The end-user 102 mayselect the health regimen data entity 202 to access additionalinformation that is included in association with the health regimen dataentity 202. The additional information may be organized in some definedway, as illustrated in organizational structure 206, or unorganized asin collection 208. The health regimen data entity 210 shows anotheralternative exemplary embodiment of the health regimen data entity 202.Here the additional information is illustrated as being included in anorganizational structure 212. One of the items of additional informationassociated with the organizational structure 212 is depicted as anotherhealth regimen data entity 214 “nested” within health regimen dataentity 212. Another of the items of additional information associatedwith the health regimen data entity 212 is linked by an item ofassociative information 216 to another health regimen data entity 218.Organizational principles such as those illustrated by the relationshipbetween health regimen data entity 212 and health regimen data entity214, and by the relationship between health regimen data entity 212,item of associative information 216, and health regimen data entity 218,may be replicated at any level of an organizational structure, or in anunorganized collection such as collection 220. It is to be understoodthat in substantially all examples referring to “an identifier forlithium” herein, analogous examples utilizing the alternatives such asthose from FIG. 2, will be recognized by those of skill in the art. Suchexamples are not expressly set forth herein for the sake of clarity.

FIG. 3 illustrates an alternative exemplary embodiment of a healthregimen data entity. Depicted is nesting health regimen data entity 300,which includes additional information relevant in the context of thenesting health regimen data entity 300, here, “constituent 1.” Theidentity of constituent 1 is not nested within nesting health regimendata entity, but an item of associative data 302 links to a healthregimen data entity 304 identifying lithium (“Li”). Also illustrated isa health regimen data entity 306 having additional information detailingpersonal notes from users of constituent 1. Shown are nested healthregimen data entity 312 and 314. The health regimen data entity 312 islinked to the nesting health regimen data entity 300 by an item ofassociative data 308 and to the health regimen data entity 304 by anitem of associative data 310.

FIG. 4 illustrates a number of alternative exemplary health regimen dataentities organized in the data structure according to differentorganizational schemes. Shown is nesting health regimen data entity 400,including three nested health regimen data entities 402, 404, and 406,for three components of a “Brand X” vitamin regimen. Depicted is nestinghealth regimen data entity 408, including a nested and nesting healthregimen data entity 410. Nested and nesting health regimen data entity410 includes nested health regimen data entities 412, 414, and 416,components of a “Brand Y” vitamin regimen. Illustrated is nesting healthregimen data entity 408 associated with health regimen data entity 306with an item of associative data 418, linking the personal notes ofhealth regimen data entity 306 with the “Brand Y” vitamin regimen ofnesting health regimen data entity 408. Illustrated is health regimendata entity 420, pertaining to “constituent 1,” including additionalinformation about personal notes, dosage, and substances. The healthregimen data entity 420 is shown linked to health regimen data entity422, identifying Lithium, by an item of associative data 424. The healthregimen data entity 406 is shown linked to another health regimen dataentity 404 by an item of associative data 426. The health regimen dataentity 314 is shown linked to the health regimen data entity 416 by anitem of associative data 428. The health regimen data entity 314 is alsoshown linked to health regimen data entity 416 by an item of associativedata 430.

The nesting as illustrated in FIGS. 2, 3, and 4 is accomplished withitems of associative information that are associated with either thenesting health regimen data entity or with one or more of theillustrated nested health regimen data entities. The nesting healthregimen data entity might represent, e.g., the name of a vitaminsupplement, and the nested health regimen data entities might represent,e.g., five constituent supplements comprised by the named vitaminsupplement. In another example, the nesting health regimen data entitiesmight represent identifiers of taxonomic classifications to which theconstituent belongs, such as chemical classes (such as water soluble orfat soluble vitamins), classes of effect or action (such asbeta-blockers, neurotransmitters, or strength enhancers).

A health regimen data entity may be associated with another healthregimen data entity in a variety of ways. The first health regimen dataentity may be associated with the second health regimen data entity withan item of associative information associated with one or the other orboth. The first health regimen data entity may be associated with thesecond health regimen data entity as well as with additional healthregimen data entities simultaneously. The multiply-referenced healthregimen data entity may actually be multiple health regimen dataentities in the data structure, or it may be a single health regimendata entity with multiple items of associative information used toreference it.

FIG. 5 depicts a number of alternative exemplary topics which may beused in the data structure. The identity of a topic may be representedby a health regimen data entity, and association with a topicaccomplished by use of an item of associative information. At least somehealth regimen data entities may be associated with topics of interestto the end-user 102 to provide a schema with which to begin use of theinformation in the data structure. Each of the topics is exemplary, butthey serve to illustrate a particular application which is not limiting.An end-user 102 may start retrieving data from the data structure bystarting with any topic in the data structure. Each item of data storedin association with each topic may have associated using an item ofassociative information with another item of data associated with thesame topic or with another topic, such that an end-user 102 startingwith an item of data in a particular topic, e.g., a name of Substance Aunder the topic Substances/Procedures, may choose to retrieve anotheritem of data associated with Substance A via a an item of associativeinformation to a health regimen data entity associated with anothertopic, e.g., a function of Substance A, relief of joint pain, associatedwith the topic Functions. The end-user 102 may continue by selecting anitem of data associated with a third topic, e.g., a Substitute B forSubstance A for the relief of joint pain, associated with the topicSubstitutes. The end-user 102 may continue in this fashion through allof the data items in the topics in the data structure associated viaitems of associative information to the selections of the end-user 102.

Although shown for clarity in FIG. 5 as discrete topics, generally,topics may be associated with or even be composed of other topics, and agiven topic or reference to that topic may be associated with anotherdiscrete topic.

The topic 500, “Substances/Procedures,” may include common, generic,commercial, and/or trade names and/or descriptions for pharmaceutical,nutraceutical, veterinary, dietary, and/or nutritional substances,procedures, processes, and/or practices of interest to an end-user 102.

The topic 502, “Functions,” may include one or more descriptions offunctions for which the substances of the topic 500,“Substances/Procedures” may be used by humans in connection with humanphysical and/or mental conditions, and/or veterinary purposes.

The topic 504, “Substitutes,” may include common, generic, commercial,and/or trade names and/or descriptions for pharmaceutical,nutraceutical, veterinary, dietary, and/or nutritional substances,procedures, processes, and/or practices of interest to an end-user 102,which may be substituted to perform functions associated with the topic502, “Functions.”

The topic 506 “Supporting Reasons,” may include explanations for thefunctionality of the substances/procedures and substitutes included inthe topics 500, “Substances/Procedures” and 504, “Substitutes.”

The topic 508, “Supporting Authorities,” may include the identities andcredentials of people and/or entities which endorse the use ofsubstances/procedures and substitutes for various functions. Thesupporting authorities may include medical and/or veterinaryprofessionals and/or experts of various kinds (“gurus”), and/ormanufacturers and/or distributors of substances/procedures andsubstitutes. The topic 508, “Supporting Authorities,” may also includetestimonials and/or reports and/or anecdotal evidence from otherend-users 102, and may include descriptors of factors associated withthose end-users 102 to permit manual or automatic correlation of theirexperience with the potential experience of the end-user 102 consultingthe data structure.

The topic 510, “Supporting Literature,” may include references topublished articles and/or other publicly available information, bycitation and/or hyperlink and/or other reference means, e.g., referredjournal articles and/or magazine articles and/or website articles,pertaining to the functionality of substances/procedures andsubstitutes.

The topic 512, “Extant Conditions,” may include one or more selectionsof descriptors that describe internal physical and/or mental and/orenvironmental and/or spiritual and/or metaphysical factors of interestto the end-user 102 and of possible relevance to the functionality ofsubstances/procedures and substitutes. Internal physical factors mayinclude body temperature, medical condition, genetic information, and/orsubstances/procedures or substitutes ingested or to be ingested. Mentalfactors may include a diagnosed mental condition, a subjective mentalstate, genetic information, and/or substances/procedures or substitutesingested or to be ingested. Environmental factors may include externaltemperature, humidity, barometric pressure, ambient light intensity,and, for some, the date, the positions of the planets, geographicalfactors such as those relevant to feng shui, and/or other factorsrelevant to disciplines, traditions, and arts considered relevant by theend-user 102 and/or by a contributor of information to the datastructure and/or by a third-party authority such as an expert or asource for acquisition. Where feasible, values for external factors maybe provided to the data structure in the form of health regimen dataentities representing the output of instrumentation, e.g., weatherinstrumentation or medical instrumentation.

The topic 514, “Sources for Acquisition,” may include identities of,contact information for, and/or channels of communication with personsand/or entities from which substances/procedures or substitutes may bepurchased or otherwise acquired by the end-user 102. Such sources maypay to be included in the data structure in association with this topic.

The topic 516, “Taxonomic Classes,” may include various categories withwhich substances/procedures and/or substitutes may be associated, e.g.acids, derivatives from X, etc.

The topic 518, “Synergies,” may include substances/procedures,substitutes activities, and/or extant conditions that, acting togetherwith a substance or substitute, enhance the functionality of thesubstance or substitute; favorably change the amount or timing or thesubstance or substitute needed for the desired functionality; and/orprovide one or more additional desirable functionalities beyond thoseassociated with the substance or substitute taken by itself.

The topic 520, “Things to Avoid,” may include substances/procedures,substitutes, activities, and/or extant conditions that, acting togetherwith a substance or substitute, detracts from the functionality of thesubstance or substitute; unfavorably changes the amount or timing or thesubstance or substitute needed for the desired functionality; and/orprovides one or more additional undesirable functionalities beyond thoseassociated with the substance or substitute taken by itself.

The topic 522, “Dosing,” may include information pertaining to the mode,amount, conditions, and/or timing of the delivery of a substance orsubstitute to achieve the desired functionality, along with synergiesand things to avoid, e.g., 200 mg capsules of Substance A, taken twicedaily when sunny and thrice daily when cloudy or raining; or once dailyunder any conditions no matter the weather, and never to be taken whenSubstance B has been taken within 24 hours. Beyond that simple example,the topic 522, “Dosing,” may include a procedure for determining anamount and/or timing for the substance to be taken, rather than a simplefixed value, along with factors that give the end-user 102 options basedon probabilities and other factors such as extant conditions, e.g., whenthe weather is hot and the end-user 102 is feeling irritable, an optionto reduce a lithium dose by one pill per day, and if that does not work,by two pills per day, but never by more than two pills per day. Theseoptions and alternatives to them may also be accessed by associationswith other health regimen data entities, including, e.g., hot days,lithium, and/or irritability.

The topic 524, “Formulations,” may include information pertaining to theconstituents of a substance, including but not limited to the identitiesof the constituents, the amounts of the constituents present per unit ofthe substance, and/or the method(s) for combining the constituents toform the substance. In particular, the amounts of the constituents maybe represented by listing the amounts numerically, and/or by a formulaor formulas from which each constituent amount may be derived either bythe end-user 102 or by computational resources associated with the datastructure. In an embodiment, the end-user 102 may follow items ofassociative information to health regimen data entities and/oradditional information that provide information on the sources offormulary information, e.g., an article on an experiment, or on theinstruments that provided the formulary information, e.g., an indicationof what the underlying methodology of selection is at least partiallybased upon (e.g., animal studies, human studies, in silico studies,speculation, anecdotal information, historical accounts, traditions,cultural practices, native practices, etc.

The topic 526, “Delivery,” may include information on methods ofdelivery, e.g., orally by capsule, orally by liquid dose, epidermally bypatch, injection by syringe, and/or internally by timed release from animplanted reservoir, and on formulations, dose sizes, and dose timingsassociated with various delivery methods.

FIG. 6 depicts an exemplary way to view a pathway of an end-user 102through data in the data structure. The end-user 102 in this exemplaryview starts with taxonomic classes, e.g. vitamins, selects a vitamin,e.g., Vitamin X, and selects an associated function, e.g., increasedenergy. The end-user 102 finds a substitute for Vitamin X for increasingenergy, e.g., Substance Y, refers to supporting authorities, e.g., aparticular columnist for a magazine, supporting literature, e.g., anarticle in JAMA, and supporting reasons, e.g., a web-based explanationfor the effects of Substance Y on energy. From there, the end-user 102calls up information on synergies, e.g., Substance Z as beingsynergistic with Substance Y, providing increased memory when they areused together, along with things to avoid, e.g., not using Substance Win conjunction with Substance X because such conjunctive use causesimpotence. The end-user 102 may consult “Extant Conditions” to learnthat Substance X has an increased effect at lower altitudes and/or whencertain planets are in a particular astrological configuration. Theend-user 102 may consult the “Dosing“topic for information on dosingunder various conditions, and she may peruse sources for acquisition toselect a mode of purchase, to conclude the purchase, and to arrange fordelivery.

FIG. 7 depicts an alternative exemplary way to view the pathway of anend-user 102 through data in the data structure depicted in FIG. 6,using as a template the depiction of FIG. 5.

FIG. 8 depicts an exemplary view of the pathway of an end-user 102through data in the data structure. The end-user 102 starts with asubstance, e.g., Substance M, and looks up functions for Substance M,e.g., protection against cancer. The end-user 102 then looks upsubstitutes for Substance M for protection against cancer, e.g.,Substance N. The end-user 102 then becomes interested in Substance N forother purposes. Going back to the topic “Substances/Procedures” to learnabout Substance N, the end-user 102 learns that Substance N is a memberof a particular taxonomic class, e.g. acids. The end-user 102 reassureshimself of the efficacy of Substance N for some other purpose, e.g.,prevention of hair loss, by consulting a supporting authority, e.g., afamous cancer researcher, supporting literature, e.g., a ScientificAmerican article, and supporting reasons, e.g., a published explanationof why Substance N prevents hair loss. The end-user 102 retrievesinformation on synergies from the use of Substance N and Substance O,e.g., enhanced prevention of hair loss and fresher breath, and on thingsto avoid, e.g., the use of Substance N with, e.g., Substance P, whichwould lead to decreased efficacy for hair loss and extensive skinrashes. The end-user 102 calls up the effects of extant conditions onthe use of Substance N, e.g., amplification of any already-presentschizophrenia when certain planets are in a particular astrologicalconfiguration. The end-user 102 finishes by retrieving dosinginformation and proceeding to purchase through a source for acquisition.

FIG. 9 depicts an alternative exemplary way to view the pathway of anend-user 102 through data in the data structure depicted in FIG. 8,using as a template the depiction of FIG. 5.

FIG. 10 depicts an exemplary way to view a branched pathway of anend-user 102 through data in the data structure. The end-user startswith a substance, e.g., Substance P, and looks up taxonomic classesassociated with for Substance P, e.g., water soluble vitamins. Theend-user 102 then looks up supporting authorities for the use of watersoluble vitamins for protection against cancer, such as a columnist in awell-known health magazine, and moves on to supporting literature, e.g.,articles in reference journals, and supporting reasons, e.g.,explanations of the functionality of water soluble vitamins forprevention of cancer. At this point, the end-user 102 remembers that afriend had been asking about the use of water soluble vitamins for otherpurposes, such as prevention of hair loss, especially in combinationwith certain procedures for their use. Leaving aside his originalsearch, the end-user 102 takes up his friend's question and looks upsynergies with regard to water soluble vitamins. After perusingsynergies, he selects a procedure, e.g., taking a particular watersoluble vitamin in conjunction with a food such as a particular fruit.He looks up supporting authorities for the efficacy of the water solublevitamin in conjunction with the fruit for preventing hair loss, e.g., amedical society. He then checks for things to avoid, such as the use ofa second vitamin that would reduce the effectiveness of the firstvitamin and the fruit, and extant conditions, such as humidity, whichmight affect the usefulness of the water soluble vitamin. Finally, helooks at the appropriate dosing for the water soluble vitamin. Havinginvestigated his friend's question, he returns to his original search.He had been looking up supporting reasons for the use of water solublevitamins to prevent cancer. He resumes his research at that point andmoves on to investigate appropriate dosing. Finally, he moves to sourcesfor acquisition of the Substance P.

FIG. 11 depicts an alternative exemplary way to view the pathway of anend-user 102 through data in the data structure depicted in FIG. 10,using as a template the depiction of FIG. 5.

The end-user 102 may search the data structure for patterns, findingcorrelations between health regimen data entities that would otherwisenot be discoverable or that would be very difficult to discover. Forexample, the end-user 102 may search for effects of Substance A on skinrashes in conditions of high humidity, searching, among other healthregimen data entities, those including anecdotal evidence from users ofSubstance A in high humidity, where the users of Substance A also hadskin rashes and reported apparent effects of Substance A on thoserashes. Such searches for correlations may include information andobservations added to the data structure by all or any of the end-users102, vendors 108, and/or publishers 112 using the data structure. Suchsearches may be used to test hypotheses about the efficacy and safety ofpharmaceutical, nutraceutical, veterinary, dietary, and/or nutritionalsubstances, procedures, processes, and/or practices of interest.

As mentioned above, end-users 102 may add health regimen data entitiesto the data structure to report experiences with the use ofsubstances/procedures. For example, an end-user 102 may integrate areport of an experience, e.g., partial success with the use of SubstanceB for reduction of hair loss in low-humidity conditions but littlesuccess in conditions of high-humidity, by selecting pre-existing healthregimen data entities with which to associate new health regimen dataentities that represent relevant elements of his report, and/or byassociating new health regimen data entities that represent relevantelements of his report with pre-existing annotations to pre-existinghealth regimen data entities added by other end-users 102 with similarreports. An end-user 102 may also add health regimen data entitiesrepresenting the results of correlative searches such as those describedabove, e.g., by adding health regimen data entities representing theresults of such a search and associating them with pre-existing healthregimen data entities associated with, e.g., a Substance C used toalleviate heartburn in connection with particular dietary conditions.

In using the data structure, the end-user 102 may impose his own schemaon the information searched and on the output of the search. Theend-user 102 may explicitly include or exclude for search purposeshealth regimen data entities representing factors such as weatherinformation or astrological information. He may include or exclude forsearch results reporting purposes various complexities, e.g., includingtables of correlations for further study, but excluding such informationand including only lists of ingredients and instructions for purposes ofmaking a particular substance for use or lists of dosages to serve asinput into medical dispensing devices, either indirectly through humaninput to devices or automatically through direct input of dosageinformation to devices.

FIG. 12 depicts a high-level logic flowchart of an operational process.Operation 1200 shows providing an interface to enable a vendor and/or apublisher to change one or more health regimen data entities (e.g.,providing an interface via the vendor interface device 114 and/or thepublisher interface device 122, using the vendor logic 116 and/or thepublisher logic 124, to add and/or delete and/or alter a health regimendata entity that is part of a data structure stored at least in part onthe computer 118 and/or the computer 126). Operation 1202 depictsaccepting input to the interface (e.g., accepting input to interface viathe vendor interface device 114 and/or the publisher interface device122, using the vendor logic 116 and/or the publisher logic 124, to addand/or delete and/or alter a health regimen data entity that is part ofa data structure stored at least in part on the computer 118 and/or thecomputer 126).

FIG. 13 shows several alternative implementations of the high-levellogic flowchart of FIG. 12. Operation 1200—providing an interface toenable a vendor and/or a publisher to change one or more health regimendata entities—may include one or more of the following operations: 1300,1302, 1304, 1306, 1308, 1310, 1312, 1314, 1316 and/or 1318. Operation1300 depicts providing an interface to enable the vendor and/or thepublisher to add a health regimen data entity to the one or more healthregimen data entities (e.g., providing an interface via the vendorinterface device 114 and/or the publisher interface device 122, usingthe vendor logic 116 and/or the publisher logic 124, by which the vendor112 and/or the publisher 120 may add a health regimen data entity to adata structure stored at least in part on the computer 118 and/or thecomputer 126). Operation 1302 shows providing an interface to enable thevendor and/or the publisher to delete a health regimen data entity fromthe one or more health regimen data entities (e.g., providing aninterface via the vendor interface device 114 and/or the publisherinterface device 122, using the vendor logic 116 and/or the publisherlogic 124, by which the vendor 112 and/or the publisher 120 may delete ahealth regimen data entity from a data structure stored at least in parton the computer 118 and/or the computer 126). Operation 1304 illustratesproviding an interface to enable the vendor and/or the publisher toalter a health regimen data entity of the one or more health regimendata entities (e.g., providing an interface via the vendor interfacedevice 114 and/or the publisher interface device 122, using the vendorlogic 116 and/or the publisher logic 124, by which the vendor 112 and/orthe publisher 120 may alter a health regimen data entity that is part ofa data structure stored at least in part on the computer 118 and/or thecomputer 126). Operation 1306 depicts providing an interface to enablethe vendor and/or the publisher to add additional information to ahealth regimen data entity of the one or more health regimen dataentities (e.g., providing an interface via the vendor interface device114 and/or the publisher interface device 122, using the vendor logic116 and/or the publisher logic 124, by which the vendor 112 and/or thepublisher 120 may add additional information to a health regimen dataentity that is part of a data structure stored at least in part on thecomputer 118 and/or the computer 126). Operation 1308 illustratesproviding an interface to enable the vendor and/or the publisher todelete additional information from a health regimen data entity of theone or more health regimen data entities (e.g., providing an interfacevia the vendor interface device 114 and/or the publisher interfacedevice 122, using the vendor logic 116 and/or the publisher logic 124,by which the vendor 112 and/or the publisher 120 may delete additionalinformation from a health regimen data entity that is part of a datastructure stored at least in part on the computer 118 and/or thecomputer 126). Operation 1310 shows providing an interface to enable thevendor and/or the publisher to alter additional information associatedwith a health regimen data entity of the one or more health regimen dataentities (e.g., providing an interface via the vendor interface device114 and/or the publisher interface device 122, using the vendor logic116 and/or the publisher logic 124, by which the vendor 112 and/or thepublisher 120 may alter additional information associated with a healthregimen data entity that is part of a data structure stored at least inpart on the computer 118 and/or the computer 126). Operation 1312illustrates providing an interface to enable the vendor and/or thepublisher to establish a linkage associated with a health regimen dataentity of the one or more health regimen data entities (e.g., providingan interface via the vendor interface device 114 and/or the publisherinterface device 122, using the vendor logic 116 and/or the publisherlogic 124, by which the vendor 112 and/or the publisher 120 mayestablish, e.g., select, a linkage associated with a health regimen dataentity of the one or more health regimen data entities that are part ofa data structure stored at least in part on the computer 118 and/or thecomputer 126). Operation 1314 shows providing an interface to enable thevendor and/or the publisher to provide an order form (e.g., providing aninterface via the vendor interface device 114 and/or the publisherinterface device 122 and the computer 118 and/or the computer 126, usingthe vendor logic 116 and/or the publisher logic 124, by which the vendor112 and/or the publisher 120 may provide an order form for acceptingorders for products and/or services such as nutraceutical substances orprocedures). Operation 1316 depicts providing an interface to enable thevendor and/or the publisher to provide a payment form (e.g., providingan interface via the vendor interface device 114 and/or the publisherinterface device 122 and the computer 118 and/or the computer 126, usingthe vendor logic 116 and/or the publisher logic 124, by which the vendor112 and/or the publisher 120 may provide a payment form for acceptingpayment for products and/or services such as dietary substances orprocedures). Operation 1318 illustrates providing an interface to enablethe vendor and/or the publisher to provide a delivery instruction form(e.g., providing an interface via the vendor interface device 114 and/orthe publisher interface device 122 and the computer 118 and/or thecomputer 126, using the vendor logic 116 and/or the publisher logic 124,by which the vendor 112 and/or the publisher 120 may provide a deliveryinstruction form for accepting delivery instructions for products and/orservices such as veterinary substances or procedure). Operation 1320shows providing an interface to enable the vendor and/or the publisherto provide a publication (e.g., providing an interface via the vendorinterface device 114 and/or publisher interface device 122 and thecomputer 118 and/or the computer 126, using the vendor logic 116 and/orthe publisher logic 124, by which the vendor 112 and/or the publisher120 may provide a publication such as a personal note regarding the useof a pharmaceutical substance or procedure). Operation 1322 depictsproviding an interface to enable the vendor and/or the publisher toenter a search term to search the one or more health regimen dataentities (e.g., providing an interface via the vendor interface device114 and/or publisher interface device 122 and the computer 118 and/orthe computer 126, using the vendor logic 116 and/or the publisher logic124, by which the vendor 112 and/or the publisher 120 may enter a searchterm such as “lithium” in a health regimen data entity or in additionaldata associated with a health regimen data entity).

FIG. 14 shows several alternative implementations of the high-levellogic flowchart of FIG. 13. Operation 1312—providing an interface toenable the vendor and/or the publisher to establish a linkage associatedwith a health regimen data entity of the one or more health regimen dataentities—may include one or more of the following operations: 1400,1402, 1404, 1406, 1408, 1410, 1412, 1414, and/or 1416. Operation 1400shows providing an interface to enable the vendor and/or the publisherto establish a health regimen data entity associated with the linkage(e.g., providing an interface via the vendor interface device 114 and/orthe publisher interface device 122, using the vendor logic 116 and/orthe publisher logic 124, by which the vendor 112 and/or the publisher120 may establish, e.g., add and/or select, a health regimen dataentity, such as the health regimen data entity 304 associated with thelinkage 310, that are parts of a data structure that is stored at leastin part on the computer 118 and/or the computer 126). Operation 1402depicts providing an interface to enable the vendor and/or the publisherto establish a linkage from a first nesting health regimen data entityto a second nesting health regimen data entity (e.g., providing aninterface via the vendor interface device 114 and/or the publisherinterface device 122, using the vendor logic 116 and/or the publisherlogic 124, by which the vendor 112 and/or the publisher 120 mayestablish, e.g., select, a linkage 418 from a first nesting healthregimen data entity, such as personal notes about usage 306, to a secondnesting health regimen data entity, such as Brand Y vitamin regimen 408,that are parts of a data structure that is stored at least in part onthe computer 118 and/or the computer 126). Operation 1404 illustratesproviding an interface to enable the vendor and/or the publisher toestablish a linkage from a nesting health regimen data entity to anested health regimen data entity (e.g., providing an interface via thevendor interface device 114 and/or the publisher interface device 122,using the vendor logic 116 and/or the publisher logic 124, by which thevendor 112 and/or the publisher 120 may establish, e.g., select, alinkage from a nesting health regimen data entity, such as an identifierfor lithium 204, to a nested health regimen data entity, such as ahealth regimen data entity 206 comprising indications, cautions, andresearch associated with lithium, that are parts of a data structurethat is stored at least in part on the computer 118 and/or the computer126). Operation 1406 illustrates providing an interface to enable thevendor and/or the publisher to establish a linkage from a first nestedhealth regimen data entity to a second nested health regimen data entity(e.g., providing an interface via the vendor interface device 114 and/orthe publisher interface device 122, using the vendor logic 116 and/orthe publisher logic 124, by which the vendor 112 and/or the publisher120 may establish, e.g., select, a linkage 428 from a first nestinghealth regimen data entity, such personal notes 314 regarding usage of asubstance, to a second nested health regimen data entity, such as aconstituent 416 in a vitamin regimen, that are parts of a data structurethat is stored at least in part on the computer 118 and/or the computer126). Operation 1408 depicts providing an interface to enable the vendorand/or the publisher to establish a linkage from a nested health regimendata entity to a nesting health regimen data entity (e.g., providing aninterface via the vendor interface device 114 and/or the publisherinterface device 122, using the vendor logic 116 and/or the publisherlogic 124, by which the vendor 112 and/or the publisher 120 mayestablish, e.g., select, a linkage 430 from a nested health regimen dataentity, such as a personal note 314 regarding usage of a substance, to anesting health regimen data entity, such as a vitamin regimen 408, thatare parts of a data structure that is stored at least in part on thecomputer 118 and/or the computer 126). Operation 1410 depicts providingan interface to enable the vendor and/or the publisher to establish alinkage from a nesting health regimen data entity to a non-nestinghealth regimen data entity (e.g., providing an interface via the vendorinterface device 114 and/or the publisher interface device 122, usingthe vendor logic 116 and/or the publisher logic 124, by which the vendor112 and/or the publisher 120 may establish, e.g., select, a linkage 216from a nesting health regimen data entity, such as a health regimen dataentity 212 comprising indications, cautions, and research informationassociated with lithium, to a non-nesting health regimen data entity,such as a health regimen data entity 218 comprising an identifier forlithium, that are parts of a data structure that is stored at least inpart on the computer 118 and/or the computer 126). Operation 1412 showsproviding an interface to enable the vendor and/or the publisher toestablish a linkage from a nesting health regimen data entity to anon-nested health regimen data entity (e.g., providing an interface viathe vendor interface device 114 and/or the publisher interface device122, using the vendor logic 116 and/or the publisher logic 124, by whichthe vendor 112 and/or the publisher 120 may establish, e.g., select, alinkage 310 from a nesting health regimen data entity, such as a healthregimen data entity 306 comprising personal notes regarding usage oflithium, to a non-nested health regimen data entity, such as a healthregimen data entity 304 comprising an identifier for lithium, that areparts of a data structure that is stored at least in part on thecomputer 118 and/or the computer 126). Operation 1414 depicts providingan interface to enable the vendor and/or the publisher to establish alinkage from a nested health regimen data entity to a non-nesting healthregimen data entity (e.g., providing an interface via the vendorinterface device 114 and/or the publisher interface device 122, usingthe vendor logic 116 and/or the publisher logic 124, by which the vendor112 and/or the publisher 120 may establish, e.g., select, a linkage froma nested health regimen data entity, such as a health regimen dataentity 212 comprising indications, cautions, and research associatedwith lithium, to a non-nesting health regimen data entity, such as ahealth regimen data entity 214 comprising an indication of depression,that are parts of a data structure that is stored at least in part onthe computer 118 and/or the computer 126). Operation 1416 depictsproviding an interface to enable the vendor and/or the publisher toestablish a linkage from a nested health regimen data entity to anon-nested health regimen data entity (e.g., providing an interface viathe vendor interface device 114 and/or the publisher interface device122, using the vendor logic 116 and/or the publisher logic 124, by whichthe vendor 112 and/or the publisher 120 may establish, e.g., select, alinkage 310 from a nested health regimen data entity, such as a healthregimen data entity 312 comprising a personal note regarding the usageof lithium, to a non-nested health regimen data entity, such as a healthregimen data entity 304 comprising an identifier for lithium, that areparts of a data structure that is stored at least in part on thecomputer 118 and/or the computer 126).

FIG. 15 depicts several alternative implementations of the high-levellogic flowchart of FIG. 12. Operation 1202—accepting input to theinterface—may include one or more of the following operations: 1500,1502, 1504, and/or 1506. Operation 1500 shows accepting input to theinterface to change the one or more health regimen data entities (e.g.,accepting input via the vendor interface device 114 and/or the publisherinterface device 122, using the vendor logic 116 and/or the publisherlogic 124 of the computer 118 and/or the computer 126, by which thevendor 112 and/or the publisher 120 may add and/or delete and/or alter ahealth regimen data entity that is part of a data structure that isstored on the computer 118 and/or the computer 126). Operation 1502depicts accepting input to the interface to place an order to the vendorand/or the publisher and/or end user (e.g., accepting input via thecomputer 118 and/or the computer 126, using the vendor logic 116 and/orthe publisher logic 124 of the computer 118 and/or the computer 126, bywhich an order for a substance and/or a procedure and/or a publicationmay be accepted from an end-user 102 and/or another vendor 112 and/oranother publisher 120). Operation 1504 illustrates accepting input tothe interface to make a payment to the vendor and/or the publisherand/or end user (e.g., accepting input via the computer 118 and/or thecomputer 126, using the vendor logic 116 and/or the publisher logic 124of the computer 118 and/or the computer 126, by which a payment for asubstance and/or a procedure and/or a publication may be accepted froman end-user 102 and/or another vendor 112 and/or another publisher 120).Operation 1506 shows accepting input to the interface to specify adelivery instruction to the vendor and/or the publisher and/or end user(e.g., accepting input via the computer 118 and/or the computer 126,using the vendor logic 116 and/or the publisher logic 124 of thecomputer 118 and/or the computer 126, by which delivery instructions fora substance and/or a procedure and/or a publication may be accepted froman end-user 102 and/or another vendor 112 and/or another publisher 120).

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies equally regardless of the particular type of signal bearingmedia used to actually carry out the distribution. Examples of a signalbearing media include, but are not limited to, the following: recordabletype media such as floppy disks, hard disk drives, CD ROMs, digitaltape, and computer memory; and transmission type media such as digitaland analog communication links using TDM or IP based communication links(e.g., packet links).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment).

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into image processing systems. That is, atleast a portion of the devices and/or processes described herein can beintegrated into an image processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical image processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, and applications programs, one or more interaction devices,such as a touch pad or screen, control systems including feedback loopsand control motors (e.g., feedback for sensing lens position and/orvelocity; control motors for moving/distorting lenses to give desiredfocuses. A typical image processing system may be implemented utilizingany suitable commercially available components, such as those typicallyfound in digital still systems and/or digital motion systems.

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into data processing systems. That is, at leasta portion of the devices and/or processes described herein can beintegrated into a data processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in any Application Data Sheet, are incorporated herein byreference, in their entireties.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of this subject matter describedherein. Furthermore, it is to be understood that the invention isdefined by the appended claims. It will be understood by those withinthe art that, in general, terms used herein, and especially in theappended claims (e.g., bodies of the appended claims) are generallyintended as “open” terms (e.g., the term “including” should beinterpreted as “including but not limited to,” the term “having” shouldbe interpreted as “having at least,” the term “includes” should beinterpreted as “includes but is not limited to,” etc.). It will befurther understood by those within the art that if a specific number ofan introduced claim recitation is intended, such an intent will beexplicitly recited in the claim, and in the absence of such recitationno such intent is present. For example, as an aid to understanding, thefollowing appended claims may contain usage of the introductory phrases“at least one” and “one or more” to introduce claim recitations.However, the use of such phrases should not be construed to imply thatthe introduction of a claim recitation by the indefinite articles “a” or“an” limits any particular claim containing such introduced claimrecitation to inventions containing only one such recitation, even whenthe same claim includes the introductory phrases “one or more” or “atleast one” and indefinite articles such as “a” or “an” (e.g., “a” and/or“an” should typically be interpreted to mean “at least one” or “one ormore”); the same holds true for the use of definite articles used tointroduce claim recitations. In addition, even if a specific number ofan introduced claim recitation is explicitly recited, those skilled inthe art will recognize that such recitation should typically beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, typicallymeans at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

1. A method related to health-related data management, the methodcomprising: providing an interface to enable a vendor and/or a publisherto change one or more health regimen data entities; and accepting inputto the interface.
 2. (canceled)
 3. (canceled)
 4. (canceled) 5.(canceled)
 6. (canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled) 10.(canceled)
 11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)15. (canceled)
 16. (canceled)
 17. (canceled)
 18. (canceled) 19.(canceled)
 20. (canceled)
 21. (canceled)
 22. (canceled)
 23. (canceled)24. (canceled)
 25. (canceled)
 26. (canceled)
 27. A system related tohealth-related data management, the system comprising: circuitry forproviding an interface to enable a vendor and/or a publisher to changeone or more health regimen data entities; and circuitry for acceptinginput to the interface.
 28. A system related to health-related datamanagement, the system comprising: means for providing an interface toenable a vendor and/or a publisher to change one or more health regimendata entities; and means for accepting input to the interface.
 29. Aprogram product, comprising: a signal-bearing medium bearing one or moreinstructions for providing an interface to enable a vendor and/or apublisher to change one or more health regimen data entities; and one ormore instructions for accepting input to the interface.
 30. (canceled)31. (canceled)
 32. The program product of claim 29, wherein the one ormore instructions for providing an interface to enable a vendor and/or apublisher to change one or more health regimen data entities furthercomprise: one or more instructions for providing an interface to enablethe vendor and/or the publisher to add a health regimen data entity tothe one or more health regimen data entities.
 33. The program product ofclaim 29, wherein the one or more instructions for providing aninterface to enable a vendor and/or a publisher to change one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher todelete a health regimen data entity from the one or more health regimendata entities.
 34. The program product of claim 29, wherein the one ormore instructions for providing an interface to enable a vendor and/or apublisher to change one or more health regimen data entities furthercomprise: one or more instructions for providing an interface to enablethe vendor and/or the publisher to alter a health regimen data entity ofthe one or more health regimen data entities.
 35. The program product ofclaim 29, wherein the one or more instructions for providing aninterface to enable a vendor and/or a publisher to change one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toadd additional information to a health regimen data entity of the one ormore health regimen data entities.
 36. The program product of claim 29,wherein the one or more instructions for providing an interface toenable a vendor and/or a publisher to change one or more health regimendata entities further comprise: one or more instructions for providingan interface to enable the vendor and/or the publisher to deleteadditional information from a health regimen data entity of the one ormore health regimen data entities.
 37. The program product of claim 29,wherein the one or more instructions for providing an interface toenable a vendor and/or a publisher to change one or more health regimendata entities further comprise: one or more instructions for providingan interface to enable the vendor and/or the publisher to alteradditional information associated with a health regimen data entity ofthe one or more health regimen data entities.
 38. The program product ofclaim 29, wherein the one or more instructions for providing aninterface to enable a vendor and/or a publisher to change one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toestablish a linkage associated with a health regimen data entity of theone or more health regimen data entities.
 39. The program product ofclaim 38, wherein the one or more instructions for providing aninterface to enable the vendor and/or the publisher to establish alinkage associated with a health regimen data entity of the one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toestablish a health regimen data entity associated with the linkage. 40.The program product of claim 38, wherein the one or more instructionsfor providing an interface to enable the vendor and/or the publisher toestablish a linkage associated with a health regimen data entity of theone or more health regimen data entities further comprise: one or moreinstructions for providing an interface to enable the vendor and/or thepublisher to establish a linkage from a first nesting health regimendata entity to a second nesting health regimen data entity.
 41. Theprogram product of claim 38, wherein the one or more instructions forproviding an interface to enable the vendor and/or the publisher toestablish a linkage associated with a health regimen data entity of theone or more health regimen data entities further comprise: one or moreinstructions for providing an interface to enable the vendor and/or thepublisher to establish a linkage from a nesting health regimen dataentity to a nested health regimen data entity.
 42. The program productof claim 38, wherein the one or more instructions for providing aninterface to enable the vendor and/or the publisher to establish alinkage associated with a health regimen data entity of the one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toestablish a linkage from a first nested health regimen data entity to asecond nested health regimen data entity.
 43. The program product ofclaim 38, wherein the one or more instructions for providing aninterface to enable the vendor and/or the publisher to establish alinkage associated with a health regimen data entity of the one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toestablish a linkage from a nested health regimen data entity to anesting health regimen data entity.
 44. The program product of claim 38,wherein the one or more instructions for providing an interface toenable the vendor and/or the publisher to establish a linkage associatedwith a health regimen data entity of the one or more health regimen dataentities further comprise: one or more instructions for providing aninterface to enable the vendor and/or the publisher to establish alinkage from a nesting health regimen data entity to a non-nestinghealth regimen data entity.
 45. The program product of claim 38, whereinthe one or more instructions for providing an interface to enable thevendor and/or the publisher to establish a linkage associated with ahealth regimen data entity of the one or more health regimen dataentities further comprise: one or more instructions for providing aninterface to enable the vendor and/or the publisher to establish alinkage from a nesting health regimen data entity to a non-nested healthregimen data entity.
 46. The program product of claim 38, wherein theone or more instructions for providing an interface to enable the vendorand/or the publisher to establish a linkage associated with a healthregimen data entity of the one or more health regimen data entitiesfurther comprise: one or more instructions for providing an interface toenable the vendor and/or the publisher to establish a linkage from anested health regimen data entity to a non-nesting health regimen dataentity.
 47. The program product of claim 38, wherein the one or moreinstructions for providing an interface to enable the vendor and/or thepublisher to establish a linkage associated with a health regimen dataentity of the one or more health regimen data entities further comprise:one or more instructions for providing an interface to enable the vendorand/or the publisher to establish a linkage from a nested health regimendata entity to a non-nested health regimen data entity.
 48. The programproduct of claim 29, wherein the one or more instructions for providingan interface to enable a vendor and/or a publisher to change one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toprovide an order form.
 49. The program product of claim 29, wherein theone or more instructions for providing an interface to enable a vendorand/or a publisher to change one or more health regimen data entitiesfurther comprise: one or more instructions for providing an interface toenable the vendor and/or the publisher to provide a payment form. 50.The program product of claim 29, wherein the one or more instructionsfor providing an interface to enable a vendor and/or a publisher tochange one or more health regimen data entities further comprise: one ormore instructions for providing an interface to enable the vendor and/orthe publisher to provide a delivery instruction form.
 51. The programproduct of claim 29, wherein the one or more instructions for providingan interface to enable a vendor and/or a publisher to change one or morehealth regimen data entities further comprise: one or more instructionsfor providing an interface to enable the vendor and/or the publisher toprovide a publication.
 52. The program product of claim 29, wherein theone or more instructions for providing an interface to enable a vendorand/or a publisher to change one or more health regimen data entitiesfurther comprise: one or more instructions for providing an interface toenable the vendor and/or the publisher to enter a search term to searchthe one or more health regimen data entities.
 53. The program product ofclaim 29, wherein the one or more instructions for accepting input tothe interface further comprise: one or more instructions for acceptinginput to the interface to change the one or more health regimen dataentities.
 54. The program product of claim 29, wherein the one or moreinstructions for accepting input to the interface further comprise: oneor more instructions for accepting input to the interface to place anorder to the vendor and/or the publisher and/or end user.
 55. Theprogram product of claim 29, wherein the one or more instructions foraccepting input to the interface further comprise: one or moreinstructions for accepting input to the interface to make a payment tothe vendor and/or the publisher and/or end user.
 56. The program productof claim 29, wherein the one or more instructions for accepting input tothe interface further comprise: one or more instructions for acceptinginput to the interface to specify a delivery instruction to the vendorand/or the publisher and/or end user.